|
Hi, currently I am operating my own overpass-api server based upon the full osm data replication. This is quite resource intensive as about 450 Gbyte of local storage are required for this as it holds ALL OSM data and can be used to query all of it. But the use-case I have only requires certain amounts of data to be available. Is someone here that could help me finding out how I can set-up the overpass server so that only the required objects get stored and updated/filtered in the overpass database to have a smaller footprint? Specifically this is the query that needs to be answered: [out:json] [timeout:25]; ( nodeamenity=toilets; wayamenity=toilets; relationamenity=toilets; ); out body;
|
|
Most systems that use Overpass in a "production" environment turn out to be not very well designed (or, to put it more favourably, turn out to be a proof of concept that has been promoted to production mode). Overpass is an all-purpose databsae system, striking a balance between being able to query very specific objects and also return data for large areas. Your use case would be much better served by an osm2pgsql import into a PostgreSQL database, using a style file that just imports toilets. However - no matter which database system you use - you need to remember one thing regarding updates: If a way gets created then the nodes it uses will not be in the update. This means if someone constructs a way from pre-existing nodes and tags it If you can live with an update frequency of once a day or less, then the least resource-intensive process might be this:
AH! I see. My knowledge of the underlying data structures isn't good enough to have seen this connection of way and nodes. Thanks a lot for pointing it out. I will give both your proposals a try - the postgresql and the overpass solution. Right now the big-full-sync works but as the machine does only have mechanical hard disks right now at the required size I fear for their lives with the minute updates running constantly. thanks a lot!
(16 Aug '20, 10:34)
bietiekay
|
